Fibre channel switching system

ABSTRACT

The Fibre Channel standard was created by the American National Standard for Information Systems (ANSI) X3T11 task group to define a serial I/O channel for interconnecting a number of heterogeneous peripheral devices to computer systems as well as interconnecting the computer systems themselves through optical fiber and copper media at gigabit speeds (i.e., one billion bits per second). Multiple protocols such as SCSI (Small Computer Serial Interface), IP (Internet Protocol), HIPPI, ATM (Asynchronous Transfer Mode) among others can concurrently utilize the same media when mapped over Fibre Channel. A Fibre Channel Fabric is an entity which transmits Fibre Channel frames between connected Node Ports. The Fibre Channel fabric routes the frames based on the destination address as well as other information embedded in the Fibre Channel frame header. Node Ports are attached to the Fibre Channel Fabric through links.

CROSS REFERENCE TO RELATED APPLICATIONS Priority Claim

This is a continuation of U.S. application Ser. No. 12/749,240, filedMar. 29, 2010, which is a divisional of U.S. patent application Ser. No.09/330,755, filed Jun. 11, 1999, now U.S. Pat. No. 7,688,735, which is adivisional of U.S. patent application. Ser. No. 08/801,471, filed Feb.18, 1997, now U.S. Pat. No. 6,185,203, all of which are herebyincorporated by reference in their entirety.

FIELD OF THE INVENTION

The present invention relates to input/output channel and networkingsystems, and more particularly to a digital switch which switches FibreChannel frames at link speeds of up to at least one gigabit per second(i.e., one billion bits per second).

BACKGROUND OF THE INVENTION

There is a never ending demand for increased computer systemperformance. A common limiting factor in computer system performance isthe path from the main central processing unit (CPU) to storage, or theI/O path. The CPU usually requires data from attached storage many timesfaster than the I/O path. Fibre Channel is a standard which addressesthis I/O bandwidth limitation.

Fibre Channel is an American National Standards institute (ANSI) set ofstandards which describes a high performance serial transmissionprotocol which supports higher level storage and networking protocolssuch as HIPPI, IPI, SCSI, IP, ATM, FDDI and others, Fibre Channel wascreated to merge the advantages of channel technology with networktechnology to create a new I/O interface which meets the requirements ofboth channel and network users. Channel technology is usuallyimplemented by I/O systems in a closed, structured and predictableenvironment where network technology usually refers to an open,unstructured and unpredictable environment.

Advantages of Fibre Channel include the following. First, it achieveshigh performance, which is a critical in opening the bandwidthlimitations of current computer to storage and computer to computerinterfaces at speeds up to 1 gigabit per second or taster. Second,utilizing fiber optic technology, Fibre Channel can overcome traditionalI/O channel distance limitations and interconnect devices over distancesof 6 miles at gigabit speeds. Third, it is high level protocolindependent, enabling Fibre Channel to transport a wide variety ofprotocols over the same media. Fourth, Fibre Channel uses fiber optictechnology which has very low noise properties. Finally, cabling issimple in that Fibre Channel typically replaces bulky copper cables withsmall lightweight fiber optic cables.

Fibre Channel supports three different topologies, point-to-point,arbitrated loop and fabric attached. The point-to-point topologyattaches two devices directly. The arbitrated loop topology attachesdevices in a loop. The fabric attached topology attaches a devicedirectly to a fabric.

A Fibre Channel fabric is an entity which switches frames betweenconnected devices. Fabric is a word which is synonymous with switch orrouter. The fabric must route the frame to the appropriate destinationport or return a busy if the port is not available.

Because of the high link speeds, Fibre Channel fabrics face uniqueproblems that are not present in current network switch design. Currentnetwork switches which support Ethernet, Fast Ethernet or AsynchronousTransfer Mode (ATM) protocols route incoming data at speeds up to ten toone hundred times slower than Fibre Channel fabrics. Current networkswitches also perform some incoming frame validation and networkstatistics collection. All these network switch features are moredifficult to implement when the incoming frame rate is high, as in thecase of Fibre Channel.

Route determination in network switches is usually performed bymicroprocessors. The requirement to route frames which are entering thefabric at speeds of up to one gigabit per second requires the fabric toroute the frame in very little time. Routing depends not only on theincoming frame address but a host of other parameters and current stateconditions as well. There are no currently available microprocessorswhich can in real time route sixteen lines of incoming frames with alink speed of 1 gigabit per second.

Frame validation creates another set of problems. In Fibre Channelfabrics frame validation must be performed at rates up to one hundredtimes faster than in Ethernet switches.

Statistics collection is also another function which must be performedin real time. Statistics collected are defined by the Fibre Channelfabric Management Information Base (MIB) and include the number offrames transmitted and received, the number of fabric rejects and fabricbusies transmitted and received, etc. Gathering statistics for sixteenone gigabit per second ports creates new challenges.

Current fabric realizations use either fast microprocessors or digitalsignal processors to perform the route determination functions.Typically, processors are single instruction devices which seriallydecode the instructions and perform the specified function. Digitalsignal processors contain parallel functions and can perform severalfunctions at one time. Still the problem exists to determine the routefor many simultaneous incoming frames at one gigabit per second. Currentfabric implementations perform routing on the order of tens ofmicroseconds to hundreds of milliseconds. Ideally, routing should beaccomplished in less than one microsecond.

Another problem with fabric realization is the support of the ArbitratedLoop topology. This topology has unique characteristics andrequirements. Current fabric implementations do not support thistopology.

Efficient support of both connection based classes of service (i.e.,Class 1) and connectionless classes of service (i.e., Class 2 and 3) isalso a challenge. A fabric must implement a different type of switchcore to implement each class of service. Coordination between thedifferent switch cores can be a burdensome task. Current fabricimplementations support either a connection based or a connectionlessswitch core. This leads to inefficiencies, e.g., a connectionless switchcore cannot switch Class 1 traffic if routes are not determined in frametime (i.e., less than one microsecond) and a connection switch core isvery inefficient when routing Class 2 and Class 3 traffic.

Another problem with fabric realization is the interconnection ornetworking of fabrics. This is a problem due to the high speedsinvolved. Determining a network route is sometimes even more difficultthan determining a local route. Destination addresses must be matchedbased not only on all bits matching but also matching a portion of theaddress. Route priorities should also be implemented to allow backuproutes to a destination.

SUMMARY OF THE INVENTION

The present invention described and disclosed herein comprises a methodand apparatus for transporting Fibre Channel frames between attacheddevices. The apparatus comprises logic which supports but is not limitedto the following features: Transport of Class 1, Class 2 and Class 3frames, Support for the Arbitrated Loop topology on each link, Supportfor fabric point-to-point topology on each link, Route determination inframe arrival time, and Interconnection or Networking of Fabrics.

In one aspect of the invention, the apparatus comprises separate portcontrol modules, one for each attached device, a central router module,a switch core module, a fabric control module and a brouter(bridge/router) module. In the preferred embodiment, the port controlmodules are connected to the router modules by separate route requestconnections and separate route response connections. Through thisstructure, route requests may be provided from the port control moduleto the router while simultaneously the router provides route requestresponses to the same port control module. Preferably, a common routerequest channel is utilized. Thus, apparatus is provided to return aroute response to a previously requesting port while other ports arearbitrating and sending route requests to the centralized router. Moregenerally, this apparatus provides for reading resource requests frommultiple requesters while at the same time returning resource grantresponses to previous requesters.

The router of the subject invention includes many advantageous aspects.In the preferred embodiment, the router includes multiple state machinesarranged in series for pipeline operation. Specifically, in thepreferred embodiment of the router, a hardware finite state machineoperates on the route request and a hardware finite state machineprovides the route response. Thus, in this embodiment, the routerincludes an input for receiving the output of the route requestgenerator of the port control module, an output for sending a routerequest response to the route request response receiver in the portcontrol module, a hardware finite state machine to receive the routerequest, and a hardware finite state machine to provide the routeresponse, in combination with a route determination system. Throughimplementation in hardware, route responses may be made in less than twomicroseconds, which permits essentially real-time routing at gigahertzfrequencies.

In yet another aspect of the router, it routes Fibre Channel frames to adestination port on the Fabric based on a selected portion of theincoming frame's destination address. In the preferred embodiment, FibreChannel FCPH protocol rules are applied to an incoming frame todetermine whether to route the frame or return a fabric reject or busyframes or to discard the frame. Validation of the routing of a FibreChannel frame is based on the rules defined in the ANSI FCPH standards.In the preferred embodiment, route requests are serviced in a roundrobin manner from multiple ports.

In another embodiment an apparatus and method is provided to storeblocked route requests until either the blocking condition resolvesitself or a specified time period expires. Thus, a method for servicingroute request from multiple attached devices where the routing issubject to blocked and unblocked conditions may be effective, where themethod comprises the steps of servicing a route request which is notblocked, but saving a blocked route request in hardware, preferably inregisters, and then servicing that request if the route changes from ablocked to an unblocked condition, in the preferred embodiment, prior tothe expiration of a specified time period, in a more general sense, theinvention manages the blocking and unblocking of multiple resourcerequests to a central resource.

In another embodiment an apparatus is provided to handle the scenariowhen a port input fifo is going to overflow with an incoming FibreChannel frame. Generally, the incoming data stream is typically providedto an encoder/decoder, from which it is supplied to a buffer. In theevent of a data overrun condition to the buffer, overrun preventionlogic causes the setting of tag bits to a condition which may berecognized downstream as indicative of a buffer overflow condition.

In another embodiment an apparatus is provided to interleave accesses bythe processor on the outgoing port bus in between outgoing frames orwhen the output fifo is full.

In another embodiment an apparatus is provided to pack requests in aregister array in order of first arrival but allow the removal of therequests from anywhere in the array.

OBJECTS OF THE INVENTION

It is an object of this invention to provide a fibre channel fabriccapable of operating at least 1 gigabit speeds.

It is yet a further object of this invention to permit the establishmentof a path through a fabric in real time at gigabit speeds.

It is yet a further object of this invention to provide 1 microsecond orless response time to fibre channel frames.

It is another object of this invention to determine in real time atgigabit speeds that no through path can be established through thefabric.

It is yet another object of this invention to provide a fibre channelfabric capable of simultaneously supporting Class 1, Class 2 and Class 3service.

It is an object of this invention to provide a fibre channel switchingfabric which supports arbitrated loop topology.

It is yet another object of this invention to provide systems andmethods adapted for interconnection of multiple fabrics.

It is yet another object of this invention to provide a system whichsupports Fabric point-to-point topology on each link.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating the use of a Fibre Channel Fabric.

FIG. 2 is a block diagram of a Fibre Channel Fabric.

FIG. 3 is a block diagram of the Fabric Control module.

FIG. 4 is a block diagram of the fabric Router.

FIG. 5 is a block diagram of the fabric Port Control.

FIG. 6 is a block diagram of the fabric Switch core

FIG. 7 is a block diagram of the Brouter Module.

FIG. 8 is a diagram of the Port Control FIFO Overrun Prevention Logic.

FIG. 9 is a diagram of the Port Control Process to Endec ArbitrationLogic.

FIG. 10 is a more detailed description of the Port Control module.

FIG. 11 is a diagram of the main Port Control FSM.

FIG. 12 is a diagram of the Port Control PCFIFO module interfacesignals.

FIG. 13 is a diagram of the Router address matching module.

FIG. 14 is a diagram of the Router Route Request Unblock Determinationmodule.

FIG. 15 is a detailed diagram of the Route Request Unblock Determinationmodule circuit.

FIG. 16 is another detailed diagram of the Route Request UnblockDetermination module circuit.

FIG. 17 is a diagram of the Blocked Route Request Table.

FIG. 18 is a diagram of the Router Control State Machine.

FIG. 19 is a diagram of the Blocked Route Request Port Register Array.

FIG. 20 is a diagram of both the Route State Table and the RouteDetermination modules.

FIG. 21 is a more detailed diagram of the Route Determination module.

FIG. 22 is a another more detailed diagram of the Route Determinationmodule.

FIG. 23 is a still another more detailed diagram of the RouteDetermination module.

FIG. 24 is a diagram of the Port Control Route Request interface module.

FIG. 25 is a diagram of the Port Control Route Response Interfacemodule.

FIG. 26 is a diagram of the Router to Port Control Route Request StateMachine.

FIG. 27 is a diagram of the Router to Port Control Route Response StateMachine.

FIG. 28 is a diagram of the Port Control to Router Interface StateMachine.

FIG. 29 is a diagram of the Hub Port Control module.

FIG. 30 is a diagram of the format of the Blocked Route Request Tableentry.

FIG. 31 is a diagram of the format of the Route Request.

FIG. 32 is a diagram of the format of the Router to Port. ControlResponse.

FIG. 33 is a diagram of the format of the Address Table entry.

FIG. 34 is a diagram of the format of the Route State Table entry.

DETAILED DESCRIPTION OF THE INVENTION Table of Contents A. DefinitionsB. Fibre Channel Fabric Model C. Fabric Control Module D. Fabric Router

1. Port Control Route Request Interface Module

2. Port Control Route Response Interface Module

3. Address Table

4. Address Match Module

5. Blocked Route Request Table

6. Blocked Route Request Port Register Array

7. Blocked Route Request Timer

8. Route Request Unblock Determination Module

9. Route Request Selector

10. Route Determination Module

11. Route State Table

12. Router Statistics Gathering Module

13. Router Control FSM

E. Port Control

1. Port Control Module

2. FIFO Overrun Prevention Logic

3. Processor/Data Arbitration Logic

4. Port Control Hub Module

F. Switch Core G. Router Module H. Other Documents A. DEFINITIONS

For expository convenience, the present invention is referred to as theFibre Channel Fabric or Fabric, the lexicon being devoid of a succinctdescriptive name for a system of the type hereinafter described.

The “Fibre Channel ANSI standard” describes the physical interface,transmission protocol and signaling protocol of a high-performanceserial link for support of the higher level protocols associated withHIPPI, IPI, SCSI, IP, ATM and others.

The “Fibre Channel Fabric” comprises hardware and software that switchesFibre Channel frames between attached devices at speeds up to onegigabit per second.

The following discussions will be made clearer by a brief review of therelevant terminology as it is typically (but not exclusively) used.

“Fibre Channel” is an American National Standard for Information Systems(ANSI) standard which defines a high performance serial link for supportof the higher level protocols associated with HIPPI, IPI, SCSI, IP, ATM,FDDI and others.

“FC-1” defines the Fibre Channel transmission protocol which includesthe serial encoding, decoding, and error control,

“FC-2” defines the signaling protocol which includes the frame structureand byte sequences.

“FC-3” defines a set of services which are common across multiple portsof a node.

“FC-4” is the highest level in the Fibre Channel standards set. Itdefines the mapping between the lower levels of the Fibre Channel andthe IPI and SCSI command sets, the HIPPI data framing, IP, and otherUpper Level Protocols (ULPs).

“Fibre” is a general term used to cover all transmission media specifiedin the ANSI X3.230 “Fibre Channel Physical and Signaling interface(FC-PH)” standard.

A “fabric” is an entity which interconnects various N_Ports attached toit and is capable of routing frames by using only the D_ID informationin the FC-2 frame header. The word Fabric can be seen as a synonym withthe word switch or router.

“Fabric topology” is a topology that uses the Destination Identifier(D_ID) embedded in the Frame Header to route the frame through a Fabricto the desired destination N_Port.

“Point-to-point topology” allows communication between N_Ports withoutthe use of a Fabric.

A “circuit” is a bidirectional path that allows communication betweentwo L_Ports.

“Arbitrated Loop topology” permits three or more L_Ports to usearbitration to establish a point-to-point circuit. When two L_Ports arecommunicating, the arbitrated loop topology supports simultaneous,symmetrical bidirectional flow.

“Link Control Facility” is a facility which attaches to an end of a linkand manages transmission and reception of data. It is contained withineach Port type.

“Port” is a generic reference to an N_Port or F_Port.

An “N_Port” is a hardware entity which includes a Link Control Facility.

An “NL_Port” is an N_Port that contains Arbitrated Loop functionsassociated with Arbitrated Loop topology.

An “F_Port” is a generic reference to an F_Port or FL_Port.

An “FL_Port” is an F_Port that contains Arbitrated Loop functionsassociated with Arbitrated Loop topology.

An “L_Port” is an N_Port or F_Port that contains Arbitrated Loopfunctions associated with Arbitrated Loop topology.

A “Node” is a collection of one or more N_Ports controlled by a levelabove FC-2.

A “dedicated connection” is a communicating circuit guaranteed andretained by the Fabric for two given N_Ports.

A “connection” is the process of creating a Dedicated Connection betweentwo N_Ports.

A “disconnection” is the process of removing a Dedicated Connectionbetween two N_Ports.

A “frame” is an indivisible unit of information used by FC-2.

“Frame content” is the information contained in a frame between itsStart-of-Frame and End-of-Frame delimiters, excluding the delimiters.

A “data frame” is a frame containing information meant for FC-4/ULP orthe Link application.

“Payload” is the contents of the Data Field of a frame, excludingOptional Headers and till bytes, if present.

“Source Identifier” or S_ID is the address identifier used to indicatethe source Port of the transmitted frame.

“Destination Identifier” or D_ID is the address identifier used toindicate the targeted destination of the transmitted frame.

“Valid frame” is a frame received with a valid Start of Frame (SOF), avalid End of Frame (FOF), valid Data Characters, and proper CyclicRedundancy Check (CRC) of the Frame Header and Data Field.

“Classes of Service” are different types of services provided by theFabric and used by the communicating N_Ports.

“Class 1” service is a service which establishes a dedicated connectionbetween communicating N_Ports.

“Class 2” service is a service which multiplexes frames at frameboundaries to or from one or more N_Ports with acknowledgement provided.

“Class 3” service is a service which multiplexes frames at frameboundaries to or from one or more N_Ports without acknowledgement.

“Intermix” is a service which interleaves Class 2 and Class 3 frames onan established Class 1 connection.

A “Gigabit Link Module” is a module which interfaces to the Endecthrough either a 10-bit or 20-bit interface and interfaces to the FibreChannel link through either a copper or fiber interface.

An “Encoder/Decoder” or Endec is a device which implements the FC-1layer protocol.

A “Router” is a module which determines the destination port from anaddress and other Fibre Channel frame parameters. It is a device whichforwards traffic between networks. The forwarding decision is based onnetwork layer information and routing tables, often constructed byrouting protocols.

A “Port Control” is a module which reads in a Fibre Channel header,requests a route and forwards the frame to the switch core.

“Credit” is the login credit which represents the number of frames thatmay be transmitted before receiving an acknowledgement or R_RDY.

“Fabric Login Protocol” is when an N_Port interchanges ServiceParameters with the Fabric by explicitly performing the Fabric Loginprotocol or implicitly through an equivalent method not defined inFC-PH.

“Application Specific Integrated Circuit” or (ASIC), an integratedcircuit designed to perform a particular function by defining theinterconnection of a set of basic circuit building blocks drawn from alibrary provided by the circuit manufacturer.

“FPGA” Field Programmable Gate Array, a gate array where the logicnetwork can be programmed into the device after its manufacture. An FPGAconsists of an array of logic elements, either gates or lookup tableRAMs, flip-flops and programmable interconnect wiring. Most FPGAs aredynamically reprogrammable, since their logic functions and interconnectare defined by RAM cells.

“FIFO” a data structure or hardware buffer from which items are takenout in the same order they were put in.

“Bridge” a device which forwards traffic between network segments basedon datalink layer information. These segments would have a commonnetwork layer address.

“Router” a device which forwards traffic between networks. Theforwarding decision is based on network layer information and routingtables, often constructed by routing protocols.

“Brouter” a device which bridges some packets (i.e. forwards based ondatalink layer information) and routes other packets (i.e. forwardsbased on network layer information). The bridge/route decision is basedon configuration information.

“Hub” a device connecting several other devices.

“Serdes” serial encoder/decoder, converts the Fibre Channel serialinterface to/from a 10 or 20 bit parallel interface.

“HIPPI” is a computer bus for use over fairly short distances at speedsof 800 and 1600 megabytes per second. HIPPI is described by the ANSIstandard X3T9/88-127.

“SCSI” or Small Computer System Interface is a standard for system-levelinterfacing between a computer and intelligent devices including harddisks, tape drives, and many more. SCSI is described by the ANSIstandard X3.131-1986 and by ISO/IEC 9316.

“ATM” or Asynchronous Transfer Mode is a method for the dynamicallocation of bandwidth using a fixed-size packet, also called a cell.

“SNMP” or Simple Network Management Protocol is an Internet Standardprotocol defined in RFC 1157, developed to manage nodes on an IPnetwork.

“MIB” or management information base is a database of managed objectsaccessed by network management protocols such as SNMP.

“Web” is the World-Wide Web, an Internet client-server distributedinformation retrieval system which originated from the CERN High-EnergyPhysics Laboratories in Geneva, Switzerland.

“Web Browser” is a program which allows a person to read informationfrom the Web. The browser gives some means of viewing the contents ofnodes (or “pages”) and of navigating from one node to another.

B. Fibre Channel Fabric Model

Referring to FIG. 1, a Fibre Channel Fabric is an entity whichtransports Fibre Channel frames between attached devices. The datatransmission between the connected device port (i.e., N_Port) and theFabric port (i.e., F_Port) is serial and consists of one or more frames.The transmission protocol and speeds along with the fabric functionalityare defined in the American National Standard for information Systems(ANSI) FCPH standard (see Other documents, section H, below).

The primary function of the Fabric is to receive frames from a sourceN_Port and route the frames to the destination N_Port whose addressidentifier is specified in the frames. Each N_Port is physicallyattached through a link to the Fabric or in the case of an ArbitratedLoop topology attached to the same loop. FC-2 specifies the protocolbetween the Fabric and the attached N_Ports. A Fabric is characterizedby a single address space in which every N_Port has a unique N_Portidentifier.

The Fabric model contains three or more F_Ports or FL_Ports. Each F_Portis attached to an N_Port through a link. Each F_Port is bidirectionaland supports one or more communication models. The receiving F_Portresponds to the sending N_Port according to the FC-2 protocol The Fabricoptionally verifies the validity of the frame as it passes through theFabric. The Fabric routes the frame to the F_Port directly attached tothe destination N_Port based on the N_Port identifier (D_ID) embedded inthe frame. The address translation and the routing mechanisms within theFabric are transparent to N_Ports.

There are two Sub-Fabric models, a Connection based model and aConnectionless based model. The Connection based Sub-Fabric providesDedicated Connections between F_Ports and the N_Ports attached to theseF_Ports. A Dedicated Connection is retained until a removal request isreceived from one of the communicating N_Ports or an exception conditionoccurs which causes the Fabric to remove the Connection. The Connectionbased Sub-Fabric is not involved in flow control which is managedend-to-end by the N_Ports. If the Fabric is unable to establish aDedicated Connection, it returns a busy or reject frame with a reasoncode.

A Connectionless Sub-Fabric is characterized by the absence of DedicatedConnections. The Connectionless Sub-Fabric multiplexes frames at frameboundaries between an F_Port and any other F_Port and between theN_Ports attached to them.

A given frame flows through the Connectionless Sub-Fabric for theduration of the routing. After the frame is routed, the ConnectionlessSub-Fabric is not required to have memory of source, routing ordestination of the frame. When frames from multiple N_Ports are targetedfor the same destination N_Port in Class 2 or Class 3, congestion offrames may occur within the Fabric. Management of this congestion ispart of the Connectionless Sub-Fabric and buffer-to-buffer flow control.

FIG. 1 shows a possible environment containing a Fibre Channel fabric.The fabric 1, 2 illustrated are connected with a mix of workstations 3,disk arrays 4, mainframe computers 5, and Personal Computers (PC) 6.Fabric interconnection is not limited to particular equipment or anetwork topology as illustrated in FIG. 1. Two types of fabrictopologies are illustrated in FIG. 1., the direct fabric attachedtopology 9 and the arbitrated loop topology 7.

The fabrics in FIG. 1 are shown interconnected or networked through alink 8. All links to the fabric can operate at either 266 Mbps, 533 Mbpsor 1.063 Gbps speeds and operate over either copper or fiber media, orany other compatible media.

FIG. 2 shows a block diagram of the fabric. The fabric is composed of afabric control module 54, a router module 52, multiple port controlmodules 51, 74, 75 a switch core module 53 and optionally one or morebrouter modules 55. As is understood in the art, the functions allocatedto these respective devices may, in alternate embodiments, be allocatedto different logical blocks.

The fabric control module 54 contains a processor and associatedhardware. The fabric control module software performs but is not limitedto the following functions: (1) Fabric power on self test, (2) Fabricconfiguration, (3) Broadcast, Simple Name, ARP and Directory servicesservers, (4) Fabric Loop Attached profile Extended link service command,(5) Management, (6) Network Management SNMP agent, (7) Web based fabricmanagement, (8) Uninterruptable power supply monitoring and control, and(9) Brouter Module Configuration/Control. The Fabric Control modulecontrols and configures the rest of the fabric but is not usuallyinvolved in the normal routing of frames.

The fabric Router 52 performs some or all of the following functions:(1) route address matching, (2) route determination based on the ANSIX3T11 rules, (3) route request blocking and unblocking, (4) switch coreprogramming 63, (5) statistics collection and (6) port control moduleroute request/response handling 59, 60, 61, 62, 66, 67, 72, 73.

The fabric Port Control modules (PCM) 51, 70, 74, 75 perform some or allof the following functions: (1) receive Fibre Channel frames from thefiber or copper media 56, 77, 78, (2) perforin frame validation, (3)send a route request to the router 59, 61, 66, 72, (4) receives a routeresponse from the router 60, 62, 63, 67, 73, (4) forwards the frame tothe switch core 57, 69, and (5) either discards the frame, modifies theframe into a fabric reject (F_RJT) or fabric busy (F_BSY) frame orforwards the frame depending on the route response from the router.

The fabric switch core 53 is a nonblocking N×N matrix switch with 36 bitwide transmit and receive I/Os. The switch core switches frames from thePCMs 51, 70, 74, 75 to the destination PCMs or Brouter Module.

The Brouter Module 55 performs some or all of the following functions:protocol bridging and/or routing function between a Fibre Channelnetwork and the network implemented by the Brouter Module. The BrouterModule “looks” like a Fibre Channel port to the rest of the switch. Thisis due to a protocol conversion function in the Brouter Module whichconverts the brouter networked frames to Fibre Channel frames. ConvertedFibre Channel frames from the Brouter Module enter the fabric switchthrough an internal port control module 70. Fibre Channel frames fromthe fabric switch core enter the Brouter Module through an internal path76.

C. Fabric Control Module

FIG. 2 shows the Fabric Control module (FCM) 54. The FCM 54 serves someor all of the following functions: configures the fabric, collects andreports network management parameters and implements the fabric definedservers such as the Simple Name Server, Directory Services, etc. The FCM54 configures the router 52, the port control modules 51, 74, 75 and thebrouter module 55.

FIG. 3 shows the Fabric Control module (FCM) in more detail. The FCM ismade up preferably of fast SRAM 82, DRAM 83, a DUART 84, flash memory 85(nonvolatile storage), a processor 81 and a Decode/DMA Control module87. The code for the processor is contained in the flash memory 85 andis copied to SRAM upon bootup. The interface to the brouter module 55allows the FCM to communicate through legacy networks such as ethernetand fast ethernet, depending on the brouter module.

The FCM is attached to the rest of the fabric in two different manners:both in-band 80 to the fabric and out of band 79 to the fabric. Thein-band connection is through the internal port control module. Thisconnection allows the Fabric Control Module to communicate with bothlocally and remotely attached Fibre Channel compliant devices via FibreChannel frames. The FCM connects out of band to the rest of the systemfor monitoring, initialization and control reasons.

D. Fabric Router

The Fabric Router 52 (FIG. 2) receives route requests generated from thePort. Control modules 59, 61, 66, 72, determines the frame route,reports the route responses to the Port Control modules 60, 62, 67, 73,programs the switch core to connect and disconnect the routes 63,manages blocked route requests and collects the routing statistics. Inthe preferred embodiment, there is one central router contained in afabric. The Router 52 connects and disconnects routes on a frame byframe basis. Since the router can determine a route in real time (i.e.,Fibre Channel frame time) the Fabric can support Class 1 frames. Therouter is realized in hardware through either an FPGA or a custom ASIC.The router is composed of thirteen functional modules as illustrated inFIG. 4:

-   -   (1) Port Control Route Request Interface (PCRRIM) 130    -   (2) Port Control Route Response Interface (PCRSPM) 144    -   (3) Address Table 132    -   (4) Address Match Module (ADM) 131    -   (5) Blocked Route Request Table Module (BRTBL) 133    -   (6) Blocked Route Request Port Register Array (BRRA) 134    -   (7) Blocked Route Request Timer (BRTMR) 135    -   (8) Route Request Unblock Determination Module (RRUNB) 136    -   (9) Route Request Selector (RRS) 137    -   (10) Route Determination Module (RDM) 138    -   (11) Route State Table (RST) 139    -   (12) Router Statistics Gathering Module (RST) 141    -   (13) Router Control FSM (RCFSM) 140.

1. Port Control Route Request Interface Module (PCRRIM)

The Port Control Route Request Interface Module (PCRRIM) 130 of FIG. 4(and FIG. 24 numeral 581) interfaces with the PCMs (51, 74, 75 of FIG.2) to read route requests and registers the route request for use by theinternal router modules. The PCRRIM FIG. 24 is composed of the followingfunctional blocks: round-robin arbitration 582, route request statemachine 583, registered route request 584, and the port winningarbitration register 585. The PCRRIM 581 is connected to each PCM (items56, 77 and 78 of FIG. 4) through a separate PCM requester signal 586.The PCRRIM 581 is also connected to each PCM through a common sharedroute request data channel 588. After a PCM captures an incoming frameand builds a route request the PCM raises the PCM route request signal586. The PCRRIM round robin arbitration block 582 will read all requestsignals and choose the requester in a round robin manner. Thisimplements requester fairness, i.e., one requester will not be able tostarve other concurrent PCM requesters. The round robin arbitrationblock 582 will notify the winning PCM requester via the route requeststate machine 583 by pulsing for one clock period the PCM acknowledgesignal 587 back to the winning PCM. During the next four clocks the PCMsends the route request over the common route request channel 588 to theregistered route request block 584. The Route Request channel isimplemented as an eight bit bus, but is not restricted to that size. Theroute request is thirty two bits and is shown in FIG. 31. The signalsare described below.

Route Request Field Description SID Mismatch Indicates that the incomingframe SID does not match the expected SID EOFrcvd Indicates that theentire frame including the EOF was received Route Direct A flag tooverride the router address matching logic. This is used to route framesfrom the fabric control module out to a specific port without the use ofthe DID field Delimiter Is an encoded field which specifies the receivedframes delimiter Destination The DID from the incoming frame. This fieldis valid Address only when the route direct flag is not set. DestinationOnly valid when the route direct flag is set, indicates port the remoteport to route the frame to. to route to

The winning PCM port number is registered 585 (FIG. 24) and held for useby the internal router modules 589. The PCRRIM is controlled by theRouter Control FSM through the request serviced signal 591. The PCRRIMwill raise the request valid signal 590 whenever it has a valid routerequest from a PCM in its register 584. The PCRRIM will halt any furtherroute request reads from the PCM until the request serviced signal 591is pulsed for one clock period by the Router Control FSM.

FIG. 26 shows the PCRRIM state machine. The state machine is describedbelow.

State Description IDLE 611 Wait for a route request from a port controlCMP_RR_VECT 612 Route robin logic, compare the current select vectorwith the port control. If a match occurs the port control is currentlyrequesting a route. SHIRT_RR_VECT 613 Shift the current select vector.WAITCLK 614 Signal the select port control module, wait one clock beforereading the route request channel for the route request. LDWORD0, 1, 2,3 Read the route request from the route request 615, 616, 617, 618channel. Since the route request channel is 8 bits wide and the routerequest is thirty two bits, four clocks are needed to read the routerequest. RTNAVAIL 619 Wait until the Main Route Control FSM signals thatthe route request is no longer needed (RTACK) then return to idle andwait for another route request from the port control modules.

2. Port Control Route Response Interface Module (PCRSPM)

As shown in FIG. 4 the Port Control Route Response Interface Module(PCRSPM) 144 interfaces with all the PCMs 114, the Route Determinationmodule 138 and the Router Control FSM module 140. The PCRSPM mainfunction is to return route responses to the PCMs 114. The PCRSPM 144 isindependent of the PCRRIM 101 which enables the router 52 toconcurrently receive route requests and send route responses. Thisseparation in function adds parallelism to the router, permits pipelinedoperation of the router and increases its performance.

As shown in FIG. 25 the PCRSPM is preferably composed of the followingfunctional blocks: the route response state machine 602 and the routeresponse register 603. The PCRSPM registers the route response 608 fromthe Route Determination module when the load route response signal 607is pulsed for one clock period by the Router Control FSM 140 (FIG. 4).When the Router Control FSM 140 pulses the send route response signal606 the route response state machine 602 will inform the PCMcorresponding to the port vector 609 by pulsing the PCM responseacknowledgement signal 604 and putting the route response on the commonroute response channel 605 for the next four clocks. FIG. 32 shows thethirty two bit route response format. An eight bit common route responsechannel is shown but a thirty two bit wide channel can be used dependingon the implementation.

FIG. 27 shows the PCRSPM state machine (item 602 of FIG. 25). The statemachine is described below.

State Description IDLE 631 Wait for main Router Control FSM to assertthe return route response signal. XMTRSP 632 Acknowledge the main RouterControl FSM that the route response will be returned. Signal thespecific port control module the route response will be on the routeresponse data channel on the next two clocks. XMT_DT0 633 Load the firsteight bits of the route response on the route response data channel.XMT_DT1 634 Load the second eight bits of the route response on theroute response data channel, return to IDLE.

3. Address Table

The Address Table 132 of FIG. 4 is initially configured by the processorin the fabric control module 122. The Address Table 132 contains entriesagainst which the incoming Fibre Channel frame destination identifier(D_ID) is compared. FIG. 33 shows the preferred address table entryformat. The address entry contains a twenty four bit address maskregister along with a twenty four bit address register. The incomingD_ID is ANDed with the address mask register and the result is comparedto the address register. This allows a match to be performed on anynumber of bits in the address. This also implements routing based on anycombination of the address domain (upper eight bits of the addressfield), area (middle eight bits of the address field) or port (lowereight bits of the address field) fields. Additional address fieldsinclude the destination port and the address priority fields. Thedestination port indicates which remote F_Port to route the frame to andthe address priority field specifies a priority for this address tableentry match. For any two address matches the address table entry matchwhich is the highest priority will be used. This implements an alternaterouting in case of port failure.

4. Address Match Module (ADM)

The Address Match module 13 (ADM) in FIG. 4 (FIG. 13 numeral 351)performs the comparison with the incoming frame D_ID address from theroute request 105 with the Address Table contents 109. The results areused by the Route determination module 138. As shown in FIG. 13 the ADM351 has as an input the twenty-four bit address to match 352, i.e., theincoming frame DID address from the route request, and returns thefollowing responses: the remote match port 354, the address matchedindication 355 and the route to control module indication 353. The ADMwill match an incoming D_ID address to all the addresses in the addresstable in one clock. The ADM logic is implemented in combinatorial logic.The ADM performs the following checks for each address table entry:

Address Match indication=(address in table=(address mask & D_ID))

The results are then priority decoded based on address prioritycontained in the address table and the resulting address match signaland port are generated. There is one special mode which is implementedwhich will preemptively route all frames to the Fabric Control moduleexcept frames originating from the Fabric Control module. This allowsthe fabric control module to process all incoming frames which is usefulwhen the fabric is functioning in certain environments.

5. Blocked Route Request Table (BRTBL)

The Blocked Route Request Table 133 (BRTBL) in FIG. 4 functions to saveblocked route requests. Preferably, it is realized by an array ofregisters. The BRTBL saves enough information to regenerate the routerequest once the blocking condition is cleared. The format of theblocked route request is shown in FIG. 30. The blocked route requestcontains the requesting PCM port, the matched destination PCM port, theblock reason, whether an EOF delimiter was received by the requestingPCM, i.e., whether the entire frame was received before the PCMrequested a route, the delimiter in the incoming frame, SOF type,whether there was an address match, whether to route to the fabriccontrol port and whether a fabric reject (F_RJT) or fabric busy (F_BSY)should be generated.

As shown in FIG. 4 the BRTBL reads the blocked route request from routerequest bus 107 when instructed to do so by the Route Control FSM 140.As shown in FIG. 17 a blocked route request is loaded upon a LOADFIFO447 signal pulse by the Router Control FSM. Blocked route requests arecleared when the CLRFIFO 448 signal is pulsed by the Router Control FSM.The port input vector, 449, selects which port location in the table toload or clear the blocked route request. There is one blocked routerequest entry for each PCM and the blocked route request is registeredso certain fields are available FIG. 4 numeral 116 to the Route RequestUnblock Determination module FIG. 4 numeral 136. As shown in FIG. 17,the BRTBL 441 contains the registered blocked route request table 442 socertain fields in the blocked route request can be monitored by otherrouter internal modules, 443, 444, 445, 446. The signals which aremonitored include whether the specific entry contains a blocked routerequest 444, the block reason 443 which includes blocked due to theremote port busy or blocked due to the remote port in a class 1connection with a port other than this one, and intermix is not supportby the remote port. Other monitored fields include whether the blockedrequest frame is a Class 1 frame as indicated by the SOF delimiter.

6. Blocked Route Request Port Register Array (BRRA)

The Blocked Route Request Port Register Array 134 (BRRA) in FIG. 4 readsin the requesting port 103 and saves it into a register array whichkeeps the PCM request order. This order is wired 118 to the RouteRequest Unblock Determination module 136. The BRRA is shown in moredetail in FIG. 19. When the LOADFIFO 483 signal from the Router ControlFSM is pulsed for one clock period the requesting PCM port 482 is savedinto position 0 numeral 489 of the register array. Register arrayentries are removed by the Route Request Unblock Determination modulethrough the CLRFIFO 488 signal and DEQRQ_SEL 485 vector, i.e., when theCLRFIFO signal is pulsed for one clock period the BRRA will unload theregister specified by the DEQRQ_SEL vector.

Position 0 numeral 489 contains the newest route request and position 16numeral 490 contains the oldest route request. Register array contentsare shifted by one, from the newest position to the oldest, when theLOADFIFO signal is pulsed to make room for the newest blocked routerequest port number. The shifting circuit must take into account ‘holes’in the register array. The algorithm identifies the first free registerarray entry closest to position 0 and shifts all the entries fromposition 0 to the free register array entry. The shifting circuitcreates a shift vector (STTMP) which is used to load the contents of theindividual register array entries. The circuit is shown below in verilogfor eight ports.

always @(F1_NULL or F2_NULL or F3_NULL or F4_NULL or F5_NULL or F6_NULLor F7_NULL or F8_NULL) begin // build fifo shift control word (indicateshow to shift fifo) casex ({F8_NULL, F7_NULL, F6_NULL, F5_NULL, F4_NULL,F3_NULL, F2_NULL, F1_NULL}) 8′b1xxxxxxx: STTMP = 8′b11111111;8′b01xxxxxx: STTMP = 8′b01111111; 8′b001xxxxx: STTMP = 8′b00111111;8′b0001xxxx: STTMP = 8′b00011111; 8′b00001xxx: STTMP = 8′b00001111;8′b000001xx: STTMP = 8′b00000111; 8′b0000001x: STTMP = 8′b00000011;8′b00000001: STTMP = 8′b00000001; default: STTMP = 8′b00000000; endcaseend // always

-   -   where F1_NULL, □, F8_NULL are true if register array position 1        to 8 (respectively) are empty.

The shifting vector is then used with the CLRFIFO signal 484 and thedequeue port signal (DEQRQ_SEL) 485 to clear the register arraycontents.

always @(posedge clk or negedge reset) begin if (!reset) FIFO2 <=NULLVALUE; else if (LOADFIFO && STTMP[1]) FIFO2 <= FIFO1; else if(CLRFIFO && DEQRQ_SEL == FIFO2) FIFO2 <= NULLVALUE; else FIFO2 <= FIFO2;end

7. Blocked Route Request Timer (BRTMR)

The Blocked Route Request Timer 135 (BRTMR) in FIG. 4 implements onetimer per PCM. The timer is enabled when a route request is blocked forthe particular PCM. The timer is disabled when the blocked route requestbecomes unblocked, The BRTMR is controlled by the Route Control FSMwhich not only enables the tinier but also indicates which timer toenable. Enabled timers are selected by the port from the incoming routerequest 104. Disabled timers are selected by the port from the routerequest selector module 146. The different timers are defined by theANSI FCPH standard. When a timeout occurs the Route Request UnblockDetermination module is signaled 119 to dequeue the blocked request assoon as possible.

8. Route Request Unblock Determination Module (RRUNB)

The Route Request Unblock Determination module 136 (RRUNB) in FIG. 4determines when and which blocked route request to unblock. The RRUNBreads information from the Blocked Route Request Table 116, the BlockedRoute Request Port Register Array 118 the Blocked Route Request Timer119 and the Route State Table 124. A more detailed view of the RRUNB isshown in FIG. 14, FIG. 15 and FIG. 16.

As shown in FIG. 14 the RRUNB 361 reads information from severalinternal router modules and determines the most recent and highestpriority blocked route request to dequeue from the Blocked Route RequestTable. The RRUNB signals the port to dequeue 371 to both the BlockedRoute Request Table and the Router Control FSM. The inputs to the RRUNBinclude the following information from the Route State Table: Port iscurrently busy signal 365 and the Port is currently in a class 1connection signal 366. The inputs to the RRUNB from the Blocked RouteRequest Table include the blocked route request indication, thedestination port in which the blocked route request is waiting for, theblock reason (whether waiting for the remote port to become free or bothfree and disconnected from a Class 1 route), and if the blocked routerequest is a Class 1 frame.

FIG. 16 shows part of the RRUNB circuit which generates intermediateterms necessary to calculate which blocked route requests to unblock.Each blocked route is waiting for certain conditions to clear from adestination port. The destination port vector 429, 431, 433, 435 is usedto select which remote signal to look at 421, 422, 423, 424, to generatethe remote status 430, 432, 434, 436. For example if a route request isblocked from port 1 the destination port which port 1 is waiting for isused to select the remote port busy signal. It is also used to selectthe “remote port is currently in a Class 1 connection signal”.

FIG. 15 shows another part of the RRUNB circuit. There are seventeendifferent DEQx_FLAGS, only two are shown for brevity, i.e., DEQ0_FLAG381 and DEQ16_FLAG 382. The DEQx_FLAG signals are generated according tothe following circuit:

DEQ0_FLAG = Timeout indication for port 0 from RTMR || ((!(remote port 0busy) && (!(block reason == wait for remote port 0 Class 1 connected &&(remote port 0 Class 1 connected))))

The timeout indication is generated from the BRTMR module 362 in FIG.14. The remote port 0 busy 430 and the remote port 0 Class 1 connectedsignals 434 are generated from the circuit described in FIG. 16. Theblock reason comes from the BRTBL 369. There is one DEQ0_FLAG signal forevery PCM.

As shown in FIG. 15 each DEQ_FLAG 381, 382 signal is input into sixteenmultiplexers 383, 384, representing the number of potentially blockedroute requests. Multiplexer numeral 383 uses the port number in the BRRAregister array in position 0, numeral 385, and multiplexer 384 uses theport number in the BRRA register array in position 16 numeral 386. Forexample if the contents of position 0 in the BRRA register array is port4 then the DEQ4_FLAG is select by multiplexer 383 and output to theDEQIND0 signal 387. The DEQIND signals 387, 388 are used as inputs tothe binary encoder block 389. The binary encoder block 389 takes thehighest DEQIND signal, DEQ16IND being higher than DEQ0IND and encodesthe value to a select 390 which selects the position in the BRRA 392,393 to dequeue 394. For example if DEQ16IND signal is set then the portnumber contained in position 16 of the BRRA is output 394 frommultiplexor 391.

FIG. 15 also describes a similar circuit which accounts for blockedroute requests for Class 1 frames. The resulting port derived from thiscircuit takes precedence to the circuit previously described. Thisallows priority dequeueing of blocked route requests for Class 1 frames.The circuit uses the DEQx_FLAGs 387, 388 generated from multiplexorsidentified by numeral 383 and 384. The DEQx_FLAGs are ANDed with theremote port Class 1 connected signals generated in FIG. 16 numerals 434,436 to form the inputs 396, 397 to the multiplexors identified bynumeral 398 and 399. The multiplexors 398, 399 select the destinationport contained in the BRRA array 400, 401. The output signals 402, 403are binary encoded 404 to take the highest input signal to select theposition in the BRRA 406, 407 to dequeue 408.

The inputs to multiplexor numeral 395 represent the oldest blocked routerequest 394 and the oldest blocked route request of a Class 1 frame 408.Multiplexor 395 will give priority to the Class 1 frame port 408 beforechoosing the oldest non-Class 1 route request 394. The resulting vector409 is the blocked route request to dequeue.

This circuit can be used to unblock other types of resources besidesFibre Channel route requests. The circuit is implemented ascombinatorial logic and selects the blocked route request within oneclock.

9. Route Request Selector (RRS)

The Route Request Selector module 137 (RRS) in FIG. 4 functions toselect between the incoming route request from the PCRRIM module 108 orthe BRTBL 115. The resulting route request is output 110 to the RouteDetermination module. The RRS is controlled by the Route Control FSM140.

10, Route Determination Module (RDM)

The Route Determination module 138 (RDM) in FIG. 4 applies rules definedin the ANSI Fibre Channel specifications to calculate how to route theincoming frame. The RDM receives the route request 110 from the RRS 137along with route context for the source and destination ports 112 fromthe Route State Table 139. The RRS outputs the route results 145, 111 toboth the Router Control FSM 140 and the PCRSPM 144. The RDM isimplemented in combinatorial logic and applied the route rules in oneclock.

FIG. 20 shows the RDM 501 in more detail. The RDM reads the routerequest from the RRS which includes the source requesting port 503, thedestination port 504, the frame SOF delimiter 505, the EOF received flag506, the route to port 0 (i.e., fabric controller) flag 507 and thetimeout indication 508. The RDM also reads in the route table contextfor both the source and destination ports 512 and reads in a test enablevector 513. The test enable vector 513 turns off selected route rulechecks for more flexibility when the router is implemented in an ASIC.The outputs from the RDM include the route results vector 509, 510 whichindicates whether to route the frame or return an error, the reject/busyaction/reason vector 10 which is valid when the RDM detects an error andthe route back indication 511 which signals the port that the frame isin error and will routed back to the same port. Finally the updatedsource and destination port contexts are updated to reflect the RDMactions 514 and wired back to the route state table 502.

FIG. 21 shows the RDM route selection logic in more detail. As mentionedearlier the inputs to the RDM include the route state context for boththe source and destination ports 522 and the route request 523. The RDMhas prewired rules checks to detect five conditions: discard frame 525,block the route request until the remote port is not busy 526, return afabric reject (F_RJT) frame 527, return a fabric busy (F_BSY) frame 528,wait until the frame is completely received 529. If all of the fourconditions are not detected then the frame should be routed successfullyto the remote port The conditions mentioned above are derived from theORing of multiple rules checks. For example the discard frame signal isderived from the ORing of five discard frame rules checks. An examplerules check is shown below.

// discard frame if local SOFc1 received and local port is in a class 1connection wire DISFRM4 = TEN[2] && DELIM == SOFn1 && SRC_CSTATE ==Connected;

The TEN[2] term above selects a bit from the test enable vector, Turningthe bit off will disable the above rules check. The rule above willassert the DISFRM4 signal if the incoming frame contains an SOFn1delimiter and the incoming port is not already in a Class 1 connection.

As shown in FIG. 21 all potential rules check results 531 are encodedand selected by using the rules checks 525, 526, 527, 528, 529 as themultiplexor selector. The routing result selected is then output 532 toboth the Router Control FSM and the PCRSPM. All rules checks arecompleted within one clock period,

Finally FIG. 22 shows how the preencoded fabric reject 544 and fabricbusy responses 548 are selected by the fabric reject 542 and fabric busy546 rules checks. The result 551 is output to the PCRSPM module to beincluded in the route response,

11. Route State Table (RST)

FIG. 4 shows the Route State Table (RST) 139. The function of the RST isto keep the current context for each port. The RST interfaces with theRoute Determination Module (RDM) 138, the Route Request UnblockDetermination Module (RRUNB) 136 and the processor in the Fabric Controlmodule 121. FIG. 20 shows the RST 502 in relation to the RDM 501. TheRST is controlled by the Router Control FSM which signals the RST 515 toeither output the source and destination context 512 or save the updatedsource and destination context 514. The RST outputs certain contextfields into the RRUNB FIG. 4 numeral 124 to assist in route requestunblocking calculation.

The RST contains a context entry for each port. The context entry isshown in FIG. 34. There are two parts to the route context: a staticportion which is updated by the processor in the Fabric Control moduleFIG. 2 numeral 54 and a dynamic portion updated by the RDM module FIG. 4numeral 138. The processor updates the static portion upon infrequentevents such as power up and fabric login. The RDM updates the dynamicportion on a per frame basis. In current commercially available fabricsa processor manages all of the route state table fields, the currentembodiment uses a register memory in the RST and the RDM to update thecontext. The table below lists the context fields.

Signal Description Destination Port If a route exists this specifies theremote port. Connected To Class 1 Destination If this port is in a Class1 connection this field Port specifies the remote port. Timer State Ifthis port is waiting for a route and a timer is enabled, this fieldspecifies the timer. Class 1 Connection This field specifies whetherthis port is currently State in a Class 1 connection. Port Busy Thisfield specifies whether this port is currently routing a frame to aremote port. Port State This field specifies the link state, whetherinitializing, offline, online, or error. Class Supported This fieldspecifies the Classes of service supported by this port. Loop PortIndication This field specifies whether this port is a loop port or apoint to point port. Port Speed This field specifies the link speed forthis port. Intermix Support This flag specifies support for Intermix forthis port. FLOGI occurred This field specifies whether a FLOGI/ACCexchange occurred.

12. Router Statistics Gathering Module (RSG)

FIG. 4, shows the Router Statistics Gathering Module (RSG) 141. The RSGgathers fabric generated statistics. The RSG is enabled by the RouterControl FSM 140 and has as inputs the source and destination ports, theroute result and the frame Class 142. The RSG is implemented in hardwarebecause of the requirement of collecting statistics at gigabit rates.

13. Router Control FSM (RCFSM)

FIG. 4 shows the Router Control FSM (RCFSM) 140. The RCFSM controls theentire router through control signals to the internal router modules147. The RCFSM state diagram is shown in FIG. 18.

The RCFSM is triggered from idle by one of three events: a processorrequest to read or write a router data structure 470, a blocked routerequest becoming unblocked 471 or an incoming route request receivedfrom a port control module signal 472. The three events are prioritizedin case of multiple simultaneous events. The priorities from high to lowinclude: 1) processor request, 2) a blocked route request becomingunblocked and 3) an incoming route request. When a processor updates anyof the router fields the router must be in a quiescent state, i.e., notupdating any data structure. When a processor requests access to arouter data structure the processor signals the RCFSM by asserting theBLKCTLREQ signal. If in idle the RCFSM enters the RTBLKED state 452 andwaits until the processor has finished its access. While in the RTBLKEDstate the RCFSM signals it is in this state by asserting the BLKCTLACKsignal. The router processor interface logic will hold of the processoraccess via a WAIT signal until the BLKCTLACK signal is enabled.

The remaining RCFSM diagram states and description is discussed below.Refer to FIG. 18 for the state diagram and to FIG. 4 for the moduledescription.

State Description DEQROUTE 467 Program RRS 137 to use the newlyunblocked route request as an input 115 CLR_FIFO 468 Signal the BRTBL133 to remove the blocked route DECODERRSP 455 Wait one clock for theRDM 138 to apply routing rules checks to the route request 110 RTOK 456The RDM 138 has determined the route is ok. Signal the RST 139 to updatethe route table, signal the RSG 141 to collect statistics for this routeand select the destination port from the ADM 131 results. RTBSY 459 TheRDM 138 has determined to return a fabric busy (F_BSY) frame to thesending port. Signal the RST 139 to update the route table, signal theRSG 141 to collect statistics and assign the destination port from thesource port (i.e., route F_BSY back to the same port). RTRJT 460 The RDM138 has determined to return a fabric reject (F_RJT) frame to thesending port. Signal the RST 139 to update the route table, signal theRSG 141 to collect statistics and assign the destination port form thesource port (i.e., route F_RJT back to the same port). RTDISCARD 461 TheRDM 138 has determined that the port control module should discard theframe. Signal the RSG 141 to collect statistics. RTWAIT_EOF 462 The RDM138 has determined that the port control module should wait until theentire frame is received before resubmitting the route request. RTBLK463 The RDM 138 has determined to block the route request. The BRTBL 133and the BRRA 134 are signaled to save the route request and save theport requesting the route. PGMSW 457 Program the switch core 123 to makea path from the source to the destination port. RTNRSP 458 Signal thePCRRSPM 144 to return a route request complete indication. LDRTSTATE 464Signal the RST 139 to update its context and signal the BRTMR 104 toenable a blocked route request timer. LD_RT 453 Signal the RRS 137 toread the route request 108 that was just read from the PCRRIM 130.SOFOREOF 454 Signal the PCRRIM 130 to fetch another route request sincethe current request is registered in the RRS 137 module. Load the routeresults from the RDM 138 into the PCRRSPM 144 (in case delimiter is anEOF). Go to the DECODERRSP 455 state if the delimiter in the routerequest is an SOF otherwise go to the EOFDELIM 465 state. EOFDELIM 465Signal the RRS 137 to use the destination port from the route context inthe RST 139. DISTIMER 466 Signal the switch core to disconnect the pathfrom the specified source port to the destination port, signal the RST139 to update the route table context to reflect the disconnected pathand signal the PCRRSPM 144 to return a route request completeindication.

E. Port Control

FIG. 2 shows the Port Control (PC) locations 51, 70, 74, 75, within thefabric block diagram. Preferably, there is one PC per port or link. ThePC interfaces with the fabric attached device through either copper orfiber media 56, 77, 78. The PC interfaces to the switch core throughtransmit 58 and receive 57 data buses and control signals. The PCinterfaces to the router through route request 59, 61, 66, 72 and routeresponse 60, 62, 67, 73 buses and control signals. Finally the PCinterfaces to the Fabric Control module through a processor interfacebus 65.

FIG. 5 shows the Port Control in more detail. Frames are received fromthe fiber or copper link 151 and enter the Endec 153. The Endecimplements the 8B/10B encoding/decoding, the loop port state machine andfabric/point-to-point state machine functions and outputs thirty two bitdata words with two bits of parity and tag information to the receiveFIFO 155. The PC contains a module which guards against a receive FIFOoverrun condition 154. Once the receive FIFO 155 starts filling, thePort Control Module (PCM) 156 reads the frame header, requests a routefrom the router 163, 164 and forwards the frame to the switch core 161,162. The PCM is configurable by the processor 170 in the Fabric Controlmodule. The Port Control also receives frames from the switch core 165,166 to be transmitted by the Endec 153.

Port Control Module (PCM)

FIG. 10 shows the Port Control Module (PCM) in more detail. The PCM isresponsible for reading a portion of the received header from the inputFIFO 250, building a route request for the router 262, 263, 264, 260,receiving the route response from the router 265, 266, 261 and eitherforwarding the frame to the switch core 249 or building a fabric reject(F_RJT) or fabric busy (F_BSY) frame and forwarding those to the switchcore. The PCM also performs miscellaneous functions such as receiveframe validation against parity errors, short frames, frames too large,tag errors and other checks.

The PCM is composed of the following four modules:

-   -   (1) Port Control FIFO Module (PCFIFO) 247    -   (2) Port Control to Router I/F Module (PCRTIF) 234    -   (3) Port Control Main Control FSM (PCFSM) 232    -   (4) Port Control Configuration/Counter Module (PCCFG) 233

1. Port Control FIFO module (PCFIFO)

FIG. 10 shows the Port Control FIFO module (PCHFO) 247. The PCFIFObuffers several words of the incoming frame with internal registers. Theregisters include four general input registers (fifo_reg0 237, fifo_reg1238, fifo_reg2 239, fifo_reg3 240), five special input registers(sof_reg 241, rctldid_reg 242, type_reg 243, param_reg 244, eof_reg 245)and a main input and output register (EDATA_OUTR 236 and SW_DATAIN 246).The input register (EDATA_OUTR) gates the data in from the input FIFO250 by asserting the FIFOREQ_signal. The output register sends the datato the switch core by asserting the SWACK_signal 249. The general andspecial input registers are loaded from the EDATA_OUTR register. Thegeneral and special registers also are connected to a multiplexor whichfeeds the SW_DATAIN register 246. The special registers allow the PCFIFOto build fabric reject (F_RJT) and fabric busy (F_BSY) frames and toinsert special EOF delimiters when the route response 261 specifies todo so.

The received destination address (D_ID) along with the SOF delimiter iswired to the PCRTIF module 254 to build the route request 260. Finallythe PCFIFO is controlled by the PCFSM 232.

The PCFIFO module performs certain frame validations. These validationsinclude parity and tag field checking and regeneration, CRC, invalidtransmit word and link down while receiving frame validations. When theframe validations fail the PCFIFO automatically inserts the appropriateEOF delimiter 251, either an EOFa, EOFni or EOFdti.

The PCFIFO will build a fabric frame reject (F_RJT) when the routeresponse from the router specifies to do so 261. The PCFIFO builds thefabric reject by changing certain fields in the frame header 241, 242,244. Since the entire header is not yet in the PCFIFO internal registersa counter is implemented to indicate when to insert the modified headerfields. The frame fields which are modified include the R_CTL field 242,the parameter field 244 and potentially the EOF delimiter 245. Inaddition if there was a payload associated with the frame it isdiscarded.

The PCFIFO will also build a fabric busy (F_BSY) frame when the routeresponse from the router response specifies to do so 261. The PCFIFOmodifies the R_CTL field 242, the type field 243 and potentially the EOFdelimiter 245. As in the F_RJT frame modification the payload for theF_BSY frame is discarded.

2. Port Control Main Control Module (PCFSM)

FIG. 10 shows the Port Control Main Control Module (PCFSM) module 232(PCM). The PCFSM controls the other modules which compose the PCM 252,258, 272. The PCFSM is triggered by a frame being received from theinput FIFO. FIG. 11 shows the PCFSM state diagram and is described indetail below.

State Description IDLE 301 Wait until the first three words of a frameare received from the input FIFO. This is the first state after a systemreset. CLRSOF 302 A frame has been received. Reset the EOF register andstart the route request signal if the frame is not a short frame.ROUTEFRM In this state the PCFSM signals the PCRTIF to send a 303 routerequest (RREQ) to the router. The PCFSM will loop in this state until aroute response (RRACK) is received back from the router. XMTFRM 304Transmit the frame through the Port Control from the input receive FIFOto the switch core. RTNRJTBSY The router has determined that a fabricreject (F_RJT) 308 or fabric busy (F_BSY) frame should be returned. TheSOF delimiter is modified along with the R_CTL field. WAITEOF 306 Waituntil an EOF is received. The Port Control usually implements cutthrough routing, i.e., when a frame is received it is forwarded to theremote before the end of frame is received. Certain conditions dictatethat the frame should be received in its entirety before beingforwarded. An example condition includes the remote port speed is lowerthan the source port. DISCRT 305 Signal the PCRTIF to send a routedisconnect request (RREQ) and loop in this state until a routedisconnected response (RRACK) signal is received. UPDATE_CDT This oneclock state is entered into after transmitting or 306 discarding aframe. If a Class 2 or Class 3 frame was operated on the EndecCREDIT_signal is pulsed. The EOF register (RESET_EOF) is cleared, theframe counter is cleared and the EOF in received FIFO counter isdecremented. WAITEOF1 309 Wait until an EOF is received from the Endecdue to a F_RJT/F_BSY frame being returned. An EOF must be received so asto not cause a transmitter underrun at the remote Endec. XMT_FRJTBSYWait until an EOF is transmitted which signals that the 10 F_RJT orF_BSY EOF was transmitted. While in the XMT_FRJTBSY state assert eitherthe xmt_frjt or xmt_fbsy signal to the PCFIFO module to specify whichframe to transmit.

3. Port Control Configuration/Counter Module (PCCFG)

FIG. 10 shows the Port Control Configuration/Counter (PCCFG) module 233.The PCCFG maintains counters and provides the processor interface 271 tothe Port Control Module. The PCCFG contains an EOF received counter 267,a current frame count register 268 and a port control configurationregister 269. The EOF received counter keeps track of the number of fullframes received by the Endec contained in the receive frame FIFO. Thecurrent frame count register monitors the current number of wordsreceived on a per frame basis. This counter is used to detect short andlong frames. Finally the port control configuration register containsmiscellaneous information/configuration information used by the PortControl module.

The port control configuration register fields are described below.

Field Bit Location Description Max Frame Size 9:0 Indicates the maximumreceive frame size in words. LISM Mode 10 The Port is currently goingthrough loop initialization indication Clear Interrupt 11 Clear the badparity notification interrupt. Pulse CDT_ line 12 Pulse the Endec creditline. Clear Interrupt 13 Clear interrupt latch Enable Remote 14 Enablepreemptive remote port Port Routing routing. This Port Number 19:16 EOFCounter 26:24 Counter value for the number of EOF delimiters receivedfrom the Endec. Frame Discarded 27 Frame was discarded by the PortControl. Frame Too Short 28 A frame which was less than eight Detectedwords in length was received. Frame Too Big 29 A frame which was greaterthan the Received specified maximum frame size (bits 9 to 0) wasreceived. Tag Error 30 A tag error was detected (i.e., a tag occurred ofeither 00 or 11). Parity Error 31 Clear parity interrupt indicationoccurred register.

4. Port Control to Router Interface Module (PCRTIF)

FIG. 10 shows the Port Control to Router Interface Module (PCRTIF) 234.The PCRTIF builds route requests for the router 260, signals the routerthat a valid request is present 262, waits for a router response validsignal (RTPCREQ) 263 and receives the router response 261. The PCRTIFbuilds the route request from the D_ID field, the SOF delimiter and somemiscellaneous signals from both the PCFIFO 254 and the PCCFG 273modules. The route request is transmitted over a shared command channelbus 264 to the router. This command channel bus is shared by all thePCMs. The route response is received over a different shared responsechannel bus (RT_DATA) 266 which is also shared by all the PCMs. Byimplementing different buses or channels for the route request and routeresponse the router can simulataneously read route requests along withreturning route responses.

FIFO Overrun Prevention Logic (FOPL)

FIG. 5 shows the FIFO Overrun Prevention Logic (FOPL) 154 within thePort Control area. The purpose of the FOPL is to handle the case wherethe FIFO 155 is full and frames are received by the Endec 153. Since theframe arrival rate is extremely fast at gigabit link data rates, theFOPL must act in real time. An additional situation the FOPL must handleis when the frame arrives and is being routed to the remote port and theback end of the frame overruns the FIFO. Still another situation iswhere multiple frames overrun the FIFO. The FOPL operates on the TAGbits 154 not the data bits 171. The Endec takes gigabit serialtransmission from the link side, decodes the transmission and outputsthirty two bit words to the port control FIFO. Along with the thirty twobit words are a two bit tag field and a two bit parity field. The tagand parity field additions are a common interface characteristics. Tagbits are bits attached to the thirty two bit words to indicateddelimiters such as the SOF or EOF. When the FIFO is full and a frame isreceived from the Endec the FOPL sets the tag bits to an illegal value.When the FIFO enters the not full condition the next word will containthe illegal tag bits. The illegal tag bits will signal the Port Controlmodue to abort the frame with the appropriate EOF delimiter.

FIG. 8 shows the FOPL in more detail. The FOPL 201 interfaces with theEndec tag bits 202, the Endec receive frame DMA request signal 203, andthe Endec receive frame DMA acknowledgement 204 signal. The FOPLinterfaces with the FIFO by supplying the tag bits and through theFIFONOTEMPTY 206 signal. During normal operation the FOPL will set thetag bits 205 to the value of the Endec tag bits 202. When the FIFO isfull, i.e., when the FIFONOTEMPTY signal 206 is deasserted, the FOPLwill output an illegal value for the tag bits 205 going to the FIFO. Ifthe overflow word is the last word to be received the FOPL will waituntil the FIFONOTEMPTY signal 206 is asserted and then output a wordwith had tag bits by asserting the FIFO WRITE 207 signal. This lastscenario handles the case where the last word received overflows theFIFO and there are no other words to receive.

Processor/Data Arbitration Logic (PDAL)

FIG. 5 shows the Processor/Data Arbitration Logic (PDAL) 157 within thePort Control area. Since the Endec 153 multiplexes the transmit bus withthe internal register configuration bus, logic is needed to arbitratebetween processor accesses 168 and frames being transmitted from theswitch core 166. This logic must manage processor accesses to the Endecwhich are slower than transmit data word dma's. In other words if aframe is currently being transmitted, processor accesses to the Endecmust be held off until either the frame transmission is complete or theinternal Endec transmit FIFO is full, allowing enough time for aprocessor access before a transmitter underrun occurs.

The PDAL acts as the arbitrator between processor accesses and transmitdata to the Endec. The PDAL accomplishes this by keeping track of whenthe switch core is transmitting frames to the Endec and insertingprocessor accesses between frames or when the Endec's internal transmitFIFO is full. FIG. 9 shows the PDAL in more detail. The PDAL interfacesto the Endec through the Endec transmit frame DMA request 209 signal,the chip select 208 and the wait 207 signals. The PDAL interfaces withthe switch core through the transmit frame dma request signal 212. ThePDAL interfaces with a bus transceiver 225 through an enable signal 216.The PDAL interfaces with the processor from the Fabric Control modulethrough the chip select 214, wait 215 and write 222 signals. Finally thePDAL interfaces to the Router Module through the route busy 226 signal.The processor will only access the Endec transmit/configuration bus 224when the wait signal 215 is deasserted. The PDAL uses two conditions tocreate the processor wait signal. The first condition is that there areno frames being transmitted to the Endec. This condition is indicated bythe route busy signal 226 from the router being deasserted. The secondcondition is the transmit frame dma request signal 209 deasserted,indicating that the internal Endec transmit FIFO is full. The secondcondition creates enough time for a processor access to the Endecinternal registers before the Endec's internal transmit FIFO empties.

Port Control Hub Module

FIG. 29 shows the Port Control Hub Module (PCHM). The PCHM extends thefunctionality of the Port Control Module by adding several Fibre ChannelArbitrated Loop Huh ports. This has the affect of leveraging a singleswitch port over multiple attached devices 705. All attached devices 705are logically on a single loop connected to the switch through aninternal Endec 700. The internal Endec is connected on the loop by botha transmit 701 and receive 702 serdes modules. The output of the serdesmodule is a gigabit serial stream of data. The loop is repeated bycommercially available 1.0625 Gbit/sec Channel Repeater/Hub Circuits 703such as Vitesses' 25, VSC7120. (See, e.g., Vitesse SemiconductorCorporation “1996 Communications Products Data Book”). The repeater/hubcircuits contain a monolithic Clock Recovery Unit (CRU), a digitalSignal Detect Unit (SDU) and a Port Bypass Circuit (PBC). Therepeater/hub circuits allow devices to attach and detach withoutinterrupting the loop. The repeater/hub circuits are connected to aGigabit Interface Converter (GBIC) module 704 which supports eithercopper or fiber media via a plug in module. All repeater/hub circuitsare controlled by the fabric control processor through a register 705.This allows the fabric control module to monitor the state of each portand integrate the status with the general switch network management.

The integral hub provides many advantages over standalone hubs. Theseadvantages include:

-   -   Leveraging the redundant power supplies and fans usually        resident in the fabric    -   Segmenting loops to allow for increased performance per loop and        greater immunity from loop failure    -   Allowing for hot pluggable hub boards    -   Leveraging the switches SNMP network management capability for        greater control and monitoring of the loop.

F. Switch Core

FIGS. 2 and 6 shows the Switch Core. The switch core implements anonblocking N×N matrix switch. The input to the switch core comes fromthe individual Port Control modules FIG. 2 numerals 57, 69 and FIG. 9183, 186. The output from the switch core is wired to the Endec FIG. 2numeral 58, FIG. 9 numeral 220 and the Brouter Module FIG. 2 numeral 76.The switch core is paths are setup and torn down by the router FIG. 2numeral 63.

G. Brouter Module

FIG. 2 numeral 55 and FIG. 7 show the Brouter Module. The Brouter Modulereceives frames from the switch core 76 and transmits frames to theinternal Port Control module 70. The Brouter Module is responsible forconverting Fibre Channel frames to frames of the connected network 68.The Brouter Module looks to the rest of the fabric like a Port Controlmodule. The Brouter module sends and receives frames which adhere to theFibre Channel protocol. The frames are converted within the Broutermodule to other network frames such as Ethernet, Fast Ethernet, orGigabit Ethernet and are transmitted out to the network connection 68.

Although the foregoing invention has been described in some detail byway of illustration and example for purposes of clarity andunderstanding, it may be readily apparent to those of ordinary skill inthe art in light of the teachings of this invention that certain changesand modifications may be made thereto without departing from the spiritor scope of the appended claims.

H. Other Documents

ANSI X3.230-1994, “Fibre Channel Physical and Signaling Interface(FC-PH)”.

ANSI X3.297-1996, “Fibre Channel Physical and Signaling Interface(FC-PH-2)”.

ANSI X3.303-1996, “Fibre Channel Physical and Signaling interface(FC-PH-3)”.

ANSI X3.272-1996, “Fibre Channel Arbitrated Loop (FC-AL)”.

ANSI X3T11 Project #1133-D, “Fibre Channel Arbitrated Loop 2 (FC-AL2)”.

ANSI X3T11/95-41, “Fibre Channel Fabric Generic Requirements (FC-FG),Rev 3.2”

ANSI X3T11 Project 1134-1) “(FC-GS2)”.

ANSI X3T11 Project 959-D “Fibre Channel Switch Topology (FC-SW)”,

ANSI X3T11 Project 1235-DT, “Fibre Channel Fabric Loop Attachment(FC-FLA) Rev 2.2”

FCA “N_Port to F_Port Interoperability Profile, Rev 1.0”

1. An interconnect system having a plurality of ports transferringreceived Fibre Channel frames between multiple attached devicescomprising, a first port control module supporting a first link speed, asecond port control module supporting a second link speed, the secondlink speed different from the first port link speed, a third portcontrol module supporting a third link speed, the third link speed isthe same as either the first port control module link speed or thesecond port control module link speed, a connectivity apparatus coupledto each port control module, affecting the transfer of frames betweenany two ports, the connectivity apparatus supporting a fixed frametransfer rate, the same for each frame transferred between any twoports.